Skip to content

Infra Update v8: spack v1 Support#46

Open
CodeGat wants to merge 10 commits intomainfrom
infra-update-v8
Open

Infra Update v8: spack v1 Support#46
CodeGat wants to merge 10 commits intomainfrom
infra-update-v8

Conversation

@CodeGat
Copy link
Member

@CodeGat CodeGat commented Nov 18, 2025 •
edited by github-actions bot
Loading

References issue ACCESS-NRI/build-cd#313 and PR ACCESS-NRI/build-cd#326
References rollout issue ACCESS-NRI/build-cd#328
References project Spack `0.22` to `1.0` Migration

Important

This PR is a major update to the deployment infrastructure. See below for the prerequisites for this repository to be able to merge this PR.

Important

This major version change marks the end of major infrastructure updates for deployments to spack < 1.0.
If you want to deploy to instances of spack < 1.0, you must use build-cd < v8.
If you want to deploy to instances of spack >= 1.0, you must use build-cd >= v8.

Background

We are moving on up to spack v1! This update to spack contains many bug fixes, optimisations and new features that can be incorporated into build-cd.

This update also contains changes that make spack v0.X incompatible with this build-cd v8 update - the most prominent one being the splitting of spacks core codebase from it's builtin spack-packages repo. This means that for provenance, one to keep track of both builtin spack-packages and our own, renamed access-spack-packages. build-cd will centrally control the version of builtin spack-packages for a given instance, and config/versions.jsons spack-packages key is renamed to access-spack-packages.

As noted earlier, this major version of build-cd can only support spack v1, due to spack v1-specific commands in the infrastructure. If you still want to deploy to spack v0.X, you will need to change build-cd to v7, and update the config/versions.json file/spack.yaml.

Features

  • Support for spack v1: We're moving to a new, non-beta version of spack! It contains bug fixes, features and optimisations over the old version.

Prerequisites for Merging

  • Update build-cd entrypoints (this PR!)
  • Update config/versions.json with new inputs (also this PR!)
  • Validate compiler additions to the spack manifest (this PR, too!)
  • Test and Verify Model built with spack v1

🚀 The latest prerelease access-esm1p5/pr46-1 at beddb0a is here: #46 (comment) 🚀

@CodeGat CodeGat added the type:infra Related to CI/CD label Nov 18, 2025
@CodeGat CodeGat self-assigned this Nov 18, 2025
@CodeGat CodeGat marked this pull request as ready for review February 16, 2026 23:04
@CodeGat CodeGat deployed to Gadi Prerelease February 16, 2026 23:10 — with GitHub Actions Active
@github-actions
Copy link

github-actions bot commented Feb 16, 2026

🚀 Attempted to deploy access-esm1p5 Prerelease pr46-1 with commit beddb0a

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.5, defined in spack.yaml, will be deployed to Gadi as:

  • 2024.12.1 as a Release (when merged).
  • pr46-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p5/pr46-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/1.1/spack in the access-esm1p5-pr46-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

@CodeGat
Copy link
Member Author

CodeGat commented Feb 17, 2026

!update-configs

@access-bot access-bot mentioned this pull request Feb 17, 2026
Draft
@github-actions
Copy link

github-actions bot commented Feb 17, 2026

🔧 Opening Model Configuration PRs in ACCESS-NRI/access-esm1.5-configs

Configurations Requested

Configurations requested from profile default:

  • dev-preindustrial+concentrations
Pull Requests Opened

The following PRs were opened:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-ESM1.5/actions/runs/22081185963

@CodeGat
Copy link
Member Author

CodeGat commented Feb 17, 2026

Given the above, this is NOT bitwise reproducible :/ ACCESS-NRI/access-esm1.5-configs#142 (comment)

@CodeGat CodeGat mentioned this pull request Feb 17, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@CodeGat CodeGat

Labels

type:infra Related to CI/CD

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@CodeGat